For a complete Exchange server backup, backup for the following components must be performed:
System State:For Exchange server with Active Directory installed, as part of the restore, the system state of the server must also be restored.
Running regular system state backups of the Exchange is therefore crucial, as it ensures that the system state data is synchronized with the Exchange database data.
Information Store (Exchange 2007):The Information Store of Exchange 2007 contains both mailbox store and public folder store data.
The server stores data into two files - .edb and .stm file that forms an Exchange store repository.
The default mailbox store on an Exchange 2007 server uses filename Priv1.edb and Priv1.stm; the default public folder store uses the filename Pub1.edb and Pub1.stm.
The .edb file contains tables that hold metadata for all e-mail messages and other items in the Exchange store, while .stm stores native Internet content.
Information Store (Exchange 2010 / 2013):The Information Store of Exchange 2010/2013 contains the data, data definitions, indexes, checksums, flags, and other information that comprise mailboxes in Exchange.
Mailbox databases hold data that's private to an individual user and contain mailbox folders generated when a mailbox is created for that user. A mailbox database is stored as an Exchange database .edb file.
Public folder databases contain the data, their definitions, indexes, checksums, flags, and other information that comprise any public folders in your Exchange organization.
In Exchange Server 2010/2013, public folders are an optional feature.
Please ensure that the following requirements are met by the MS Exchange server:
Please ensure that the following requirements are met by the MS Exchange server:
The Exchange server 2010 backup does not requires spooling the database to the hard disk, however the VSS Exchange backup still requires certain amount of disk space to operate. Microsoft suggested that some shadow copy mechanism may required to reserve 100% of the original database.
Reference: http://msdn.microsoft.com/en-us/library/exchange/aa579091%28v=exchg.140%29.aspx
Please ensure that the following requirements are met by the MS Exchange server:
The Exchange server 2013 backup does not requires spooling the database to the hard disk, however the VSS Exchange backup still requires certain amount of disk space to operate. Microsoft suggested that some shadow copy mechanism may required to reserve 100% of the original database.
Reference: http://msdn.microsoft.com/en-us/library/exchange/aa579091%28v=exchg.140%29.aspx
Please ensure that the following requirements are met by the MS Exchange server:
The Exchange server 2010 backup does not requires spooling the database to the hard disk, however the VSS Exchange backup still requires certain amount of disk space to operate. Microsoft suggested that some shadow copy mechanism may required to reserve 100% of the original database.
Reference: http://msdn.microsoft.com/en-us/library/exchange/aa579091%28v=exchg.140%29.aspx
Scheduled backup on DAG is required, as all the %edition_name% on different Exchange servers will base on the scheduled backup time to activate all the backups at the same time.
Scheduled backup on DAG is required, as all the %edition_name% on different Exchange servers will base on the scheduled backup time to activate all the backups at the same time, even all these Exchange servers are located at different timezones. When the backup on all Exchange servers are finished, a single email report will be generated.
The scheduler would refers to the system clock on the client machine for stand-alone Exchange server backup.
The scheduler would refers to the timezone setting of the corresponding %edition_name% account’s profile (instead of the system clock on the client machine for stand-alone Exchange server backup).
Manual backup on each nodes are not considered as a complete Exchange DAG backup, as the job ran on individual Exchange DAG member, passive database copy(s) are skipped.
The backup module protects the Exchange at a database level, if full system backup is required, please run the full Windows system backup on each Exchange server within the DAG.
To backup mailbox database within an Exchange DAG, %edition_name% is required to be installed on each DAG member with Mailbox Role (e.g. servers that are hosting the mailbox databases). It is not necessary to install %edition_name% on Exchange server with CAS (Client Access Server) Role only.
Please ensure that the following requirements are met by the MS Exchange server:
The Exchange server 2013 backup does not requires spooling the database to the hard disk, however the VSS Exchange backup still requires certain amount of disk space to operate. Microsoft suggested that some shadow copy mechanism may required to reserve 100% of the original database.
Reference: http://msdn.microsoft.com/en-us/library/exchange/aa579091%28v=exchg.140%29.aspx
Scheduled backup on DAG is required, as all the %edition_name% on different Exchange servers will base on the scheduled backup time to activate all the backups at the same time.
Scheduled backup on DAG is required, as all the %edition_name% on different Exchange servers will base on the scheduled backup time to activate all the backups at the same time, even all these Exchange servers are located at different timezones. When the backup on all Exchange servers are finished, a single email report will be generated.
The scheduler would refers to the system clock on the client machine for stand-alone Exchange server backup.
The scheduler would refers to the timezone setting of the corresponding %edition_name% account’s profile (instead of the system clock on the client machine for stand-alone Exchange server backup).
Manual backup on each nodes are not considered as a complete Exchange DAG backup, as the job ran on individual Exchange DAG member, passive database copy(s) are skipped.
The backup module protects the Exchange at a database level, if full system backup is required, please run the full Windows system backup on each Exchange server within the DAG.
To backup mailbox database within an Exchange DAG, %edition_name% is required to be installed on each DAG member with Mailbox Role (e.g. servers that are hosting the mailbox databases). It is not necessary to install %edition_name% on Exchange server with CAS (Client Access Server) Role only.
Field | Description |
Name | This is the name of the backup set. You can create a meaningful name for it. |
Backup Type | Enter the correct backup type from the drop down box. |
Version | Version of the Exchange server. |
To create a backup set name: